Systems and methods to generate agendas for group meetings

ABSTRACT

Systems and methods for generating an agenda for a group meeting are disclosed. Exemplary implementations may: manage environment state information maintaining a collaboration environment, the collaboration environment being configured to facilitate interaction by users with the collaboration environment; obtain user input information conveying user input to initiate individual group meetings with individual groups of users; responsive to obtaining the user input information: identify the individual groups of users corresponding to the individual group meetings, and/or identify the work unit records corresponding to the individual group meetings; generate agenda information defining individual agendas for the individual group meetings, the individual agendas including individual sets of agenda items, an individual agenda item corresponding to an individual work unit record; and/or perform other operations.

FIELD OF THE DISCLOSURE

The present disclosure relates to systems and methods to generateagendas for group meetings.

BACKGROUND

Collaboration environments, sometimes referred to as integratedcollaboration environments, may enable users to assign projects, tasks,and/or other units of work to assignees (e.g., other users) to complete.A collaboration environment may comprise a virtual environment in whicha team of users does its work. A collaboration environment may enableusers to work in a more organized and efficient manner. A collaborationenvironment may integrate additional features and/or functionality suchas web-based conferencing and collaboration, desktop videoconferencing,instant messaging, and/or other features into a single easy-to-use,intuitive interface.

SUMMARY

One aspect of the present disclosure relates to a system configured togenerate agendas for group meetings. Traditionally, when meetings arescheduled, agenda items and other relevant information may not bereadily accessible. Manual navigation through a collaborationenvironment may be required to obtain relevant information to themeeting. Sometimes relevant information may get lost in communications(e.g., via E-mail, chats, comments, etc.). One or more implementationsdescribed herein may automatically determine agenda items for individualgroup meetings for groups users. Such agenda items may be based on oneor more of the users in a group, units of work corresponding with theusers participating in the meeting, particular date ranges, and/or otherinformation related to units of work and/or the users themselves. Thisautomation of agenda items may reduce time spent manually searchingand/or obtaining relevant information for units of work to discussduring the group meetings.

One or more implementations of a system to generate an agenda for groupmeetings may include one or more hardware processors configured bymachine-readable instructions. Machine-readable instructions may includeone or more instruction components. The instruction components mayinclude computer program components. The instruction components mayinclude one or more of an environment state component, a meetingcomponent, a work unit component, an agenda generation component, and/orother instruction components.

The environment state component may be configured to manage environmentstate information maintaining a collaboration environment. Thecollaboration environment may be configured to facilitate interaction byusers with the collaboration environment. The environment stateinformation may include work unit records of units of work created by,assigned to, and/or completed by the users within the collaborationenvironment.

The meeting component may be configured to obtain user input informationand/or other information. The user input information may convey userinput to initiate individual group meetings with individual groups ofusers. By way of non-limiting illustration, user input information mayconvey user input from a first user to initiate a first group meetingwith a first group of users.

The work unit component may be configured to identify the individualgroups of users corresponding to the individual group meetings inresponse to obtaining user input information and/or other information.The work unit component may be configured to identify the work unitrecords corresponding to the individual group meetings in response toobtaining user input information and/or other information. By way ofnon-limiting illustration, responsive to obtaining the user input fromthe first user, the users in the first group of users may be identifiedand/or a first set of work unit records may be identified.

The agenda generation component may be configured to generate agendainformation defining individual agendas for the individual groupmeetings. The individual agendas may include individual sets of agendaitems and/or other information. An individual agenda item may correspondto an individual work unit record identified as corresponding to anindividual group meeting. The individual agenda items may include,and/or facilitate access to, the corresponding ones of the individualwork unit records. By way of non-limiting illustration, the agendainformation may define a first agenda for the first group meeting. Thefirst agenda may include a first set of agenda items and/or otherinformation. The individual agenda items in the first set of agendaitems may correspond to individual work unit records in the first set ofwork unit records.

As used herein, any association (or relation, or reflection, orindication, or correspondency) involving servers, processors, clientcomputing platforms, and/or another entity or object that interacts withany part of the system and/or plays a part in the operation of thesystem, may be a one-to-one association, a one-to-many association, amany-to-one association, and/or a many-to-many association or N-to-Massociation (note that N and M may be different numbers greater than 1).

As used herein, the term “manage” (and derivatives thereof) may includeactive and/or passive direction, recommendation, suggestion, approval,rejection to users within a collaboration environment and/or anycombination thereof. As used herein, the term “obtain” (and derivativesthereof) may include active and/or passive retrieval, determination,derivation, transfer, upload, download, submission, and/or exchange ofinformation, and/or any combination thereof. As used herein, the term“identify” (and derivatives thereof) may include searching, analyzing,classifying, or describing information, and/or any combination thereof.As used herein, the term “generate” (and derivatives thereof) mayinclude create, develop, and/or set up and/or any combination thereof.

These and other features, and characteristics of the present technology,as well as the methods of operation and functions of the relatedelements of structure and the combination of parts and economies ofmanufacture, will become more apparent upon consideration of thefollowing description and the appended claims with reference to theaccompanying drawings, all of which form a part of this specification,wherein like reference numerals designate corresponding parts in thevarious figures. It is to be expressly understood, however, that thedrawings are for the purpose of illustration and description only andare not intended as a definition of the limits of the invention. As usedin the specification and in the claims, the singular form of “a”, “an”,and “the” include plural referents unless the context clearly dictatesotherwise.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a system configured to generate agendas for groupmeetings, in accordance with one or more implementations.

FIG. 2 illustrates a method to generate agendas for group meetings, inaccordance with one or more implementations.

FIG. 3 illustrates an exemplary user interface, in accordance with oneor more implementations.

FIG. 4 illustrates an exemplary user interface, in accordance with oneor more implementations.

FIG. 5 illustrates an exemplary user interface, in accordance with oneor more implementations.

DETAILED DESCRIPTION

FIG. 1 illustrates a system 100 configured to generate agendas for groupmeetings, in accordance with one or more implementations. One or moreimplementations described herein may determine agenda items for groupmeetings including groups of users. A group meeting may comprise ameeting that is distinct from a one-on-one meeting. A group of users fora group meeting may refer to three or more users. A group of users maybe users who are part of a same team, working on a same project (e.g.,an organized set of units of work), and/or identified in other ways. Theagenda items may be determined based on units of work corresponding withone or more of the users participating in a meeting, particular dates ofthe units of work, and/or other information related to units of workand/or the users themselves. This automation of agenda items may reducetime spent manually searching and/or obtaining relevant information todiscuss during such meetings.

In some implementations, system 100 may include one or more of one ormore servers 102, one or more client computing platforms 104, externalresources 126, and/or other components. Server(s) 102 may be configuredto communicate with one or more client computing platforms 104 accordingto a client/server architecture and/or other architectures. Clientcomputing platform(s) 104 may be configured to communicate with otherclient computing platforms via server(s) 102 and/or according to apeer-to-peer architecture and/or other architectures. Users may accesssystem 100 via client computing platform(s) 104.

Server(s) 102 may include one or more of non-transitory electronicstorage 128, one or more processors 130 configured by machine-readableinstructions 106, and/or other components. Machine-readable instructions106 may include one or more instruction components. The instructioncomponents may include computer program components. Executing themachine-readable instructions 106 may cause server(s) 102 to facilitategenerating agendas for group meetings. The instruction components mayinclude one or more of an environment state component 108, a meetingcomponent 110, a work unit component 112, an agenda generation component114, and/or other instruction components.

Environment state component 108 may be configured to manage environmentstate information and/or other information for maintaining acollaboration environment. Managing may include one or more ofobtaining, storing, modifying, updating, and/or other processes. Thecollaboration environment may be configured to facilitate interaction byusers with the collaboration environment. The environment stateinformation may include work unit records of units of work created by,assigned to, and/or completed by the users within the collaborationenvironment. In some implementations, units of work created by, assignedto, and/or completed by the users may refer generally to a linking ofthe units of work with the individual users in the collaborationenvironment. A unit of work may be linked with a user in a manner thatdefines one or more relationships between the user and the unit of work.Such a relationship may connote and/or be a result of an action (past,present, and/or future) of the user with respect to the unit of work.Such actions may include one or more of creating a work unit record fora unit of work, being assigned to participate in a unit of work,participating in a unit of work, being granted access to a work unitrecord of a unit of work, adjusting a value of a parameter of a workunit record of a unit of work, and/or other actions.

The environment state information may include one or more of userinformation, work information, and/or other information used to define,support, and/or otherwise maintain a collaboration environment. In someimplementations, environment state information may be updated as userscontinue to interact with the collaboration environment over time. Theenvironment state component 108 may store and/or archive the environmentstate information periodically and/or based on user request to archiveand/or generate historical state information. By way of non-limitingillustration, the historical environment state information may specifyhistorical values of one or more parameters, and/or other information.

The user information may include values of user parameters. The valuesof the user parameters may be organized in user records corresponding tousers interacting with and/or viewing the collaboration environment. Thevalues of the user parameters associated with the users interacting withand/or viewing the collaboration environment may include informationdescribing the users, their actions within the collaborationenvironment, their settings, and/or other user information; and/ormetadata associated with the users, their actions within theenvironment, their settings, and/or other user information. Individualones of the users may be associated with individual ones of the userrecords. A user record may define values of the user parametersassociated with a given user interacting with and/or viewing thecollaboration environment.

The values of the user parameters may, by way of non-limiting example,specify one or more of: a name, a user name, a group parameter, a useraccount, user role information, a user department, descriptive usercontent, a to-email, a from-email, a photo, an organization, aworkspace, one or more projects (which may include project parametersdefined by one or more work unit records), one or more items of work(which may include one or more unit of work parameters defined by one ormore unit of work records), one or more user comments, one or more teamsthe user belongs to, one or more of the user display settings (e.g.,colors, size, project order, task order, other unit of work order,etc.), one or more authorized applications, one or more interactionparameters (e.g., indicating a user is working on/worked on a given unitof work, a given user viewed a given work unit of work, a given userselected a given unit of work, a timeframe in which a given user lastinteracted with and/or worked on a given unit of work, a time periodthat a given unit of work has been idle, and/or other interactionparameters), a presence parameter (e.g., indicating presence and/orinteraction level at an environment level, unit of work level, projectlevel, task level, application level, etc.), one or more notificationsettings, one or more progress parameters, status information for one ormore work units the user is associated with (units of work assigned tothe user, assigned to other users by the user, completed by the user,past-due date, and/or other information), one or more performancemetrics of a given user (e.g., how many units of work the user hascompleted, how quickly the user completed the units of work, how quicklythe user completes certain types of work units, the efficiency of theuser, bandwidth of the user, activity level of the user, etc.),application access information (e.g., username/password for one or morethird-party applications), one or more favorites and/or priorities,schedule information, meeting information, other user parameters for thegiven user.

User role information may specify individual roles of the individualusers. A role may represent a position of an individual user. Theposition may be specified based on a description of one or more of jobtitle, level, stage, and/or other descriptions of position. The role maybe specified with respect to a company as a whole, a particular unit ofwork, and/or other considerations. By way of non-limiting illustration,a role may include one or more of chief executive officer (or otherofficer), owner, manager, supervisor, accountant, associate, employee,intern, entry level, midlevel, senior, administrator, director, foreman,engineer, product developer, human resource officer, artist, artdirector, and/or other descriptions. In some implementations, roles ofusers may be defined by a role hierarchy. A role hierarchy may conveyindividual positions of individual roles in the role hierarchy. By wayof non-limiting illustration, a position may specify one or more of arole being superior to an other role, a role being subordinate to another role, and/or other information. One or more features and/orfunctionality described herein may have some restrictions placed on itby virtue of a role of a user.

Schedule information for the individual users may include one or morecalendar entries associated with the individual users. The individualcalendar entries may be associated with individual start dates and/orindividual end dates. In some implementations, schedule information maybe stored locally within electronic storage 128 by virtue of featuresand/or functionality provided within a collaboration environment. By wayof non-limiting illustration, a collaboration environment may have thefeatures and/or functionality of calendar applications configured tofacilitate calendaring entries into a schedule. It is noted thatschedule information may be determined through features and/orfunctionality provided by one or more external resources 126. By way ofnon-limiting illustration, an external resource may include a calendarapplication which may be external to a collaboration environment. Thecollaboration environment may have permissions to access the externalcalendar application to determine and/or obtain schedule information.

Meeting information for individual users may include values of a meetingparameter for the individual user. The values of the meeting parameterfor the individual users may reflect a desire to include the individualuser in the individual group meetings. The values of the meetingparameter for a given user may indicate a specific group the user may bepart of.

The work information may include values of one or more work unitparameters. The values of the work unit parameters may be organized inwork unit records corresponding to units of work managed, created,completed, and/or assigned to individual users within the collaborationenvironment. A given work unit may have one or more assignees and/orteam members working on the given unit of work. Units of work maycorrespond to one or more to-do items, action items, objectives, and/orother units of work one or more users should accomplish and/or plan onaccomplishing. Units of work may be created by a given user for thegiven user and/or created by the given user and assigned to one or moreother users. A given unit of work may include one or more or a project,a task, a sub-task, and/or other units of work possibly assigned toand/or associated with one or more users. A project may include a set ofone or more units of work.

In some implementations, individual sets of work unit records may bedefined by a record hierarchy. A record hierarchy may convey individualpositions of work unit records (and their corresponding units of work)in the record hierarchy. By way of non-limiting illustration, a positionmay specify one or more of a work unit record being superior to anotherwork unit record, a work unit record being subordinate to another workunit record, and/or other information. As a result, individual work unitrecords in the individual sets of work unit records may be subordinateto other individual work unit records in the individual sets of workunit records. For example, a work unit record may define a unit of workcomprising a task, and a subordinate work unit record may define a unitof work comprising a sub-task to the task. A record hierarchy may definea relationship between work unit records. A work unit record may havesome restrictions placed on it by virtue of having a subordinate workunit record. By way of non-limiting illustration, a work unit record maybe restricted from access by one or more users unless and/or until asubordinate work unit record is completed and/or started.

Individual work units records may include hierarchical informationdefining a record hierarchy of the individual work unit records. Thehierarchical information of a work unit record may include one or moreof information identifying other work unit records associated in arecord hierarchy the work unit record belongs to, a specification of theposition of the work unit record in the hierarchy, restrictions and/orother relationships placed on the work unit record by virtue of itsposition, and/or other information.

In some implementations, as a consequence of the record hierarchies, theindividual units of work described in the individual work unit recordsthat are subordinate to the other individual work unit records may besubordinate to the individual units of work in the other individual workunit records.

In some implementations, the one or more work unit parameters mayinclude one or more of a work assignment parameter, a work managementparameter, a work creation parameter, a meeting parameter, and/or otherparameters. The values of the work assignment parameter may describeunits of work assigned to the individual users. The values of the workmanagement parameter may describe units of work managed by theindividual users. The values of the work creation parameter may describeunits of work created by the individual users. The values of a meetingparameter for the individual units of work may reflect a desire toinclude the individual units of work in the individual group meetings(see, e.g., work unit component 112 described herein).

In some implementations, the units of work may be described based on oneor more of a unit of work name, a unit of work description, one or moreunit of work dates (e.g., a start date, a due date, a completion date,and/or dates), one or more members associated with a unit of work (e.g.,an owner, one or more other project/task members, member accessinformation, and/or other unit of work members and/or memberinformation), a status parameter (e.g., an update, a hardcoded statusupdate, a completed/uncomplete/mark complete, a measured status, aprogress indication, quantity of sub-work units remaining for a givenunit of work, completed work units in a given project, and/or otherstatus parameter), one or more user comment parameters (e.g., permissionfor who may comment such as a creator, a recipient, one or morefollowers, and/or one or more other interested parties; content of thecomments; one or more times; presence or absence of the functionality ofup-votes; one or more hard-coded responses; and/or other parameters),one or more interaction parameters (e.g., indicating a given unit ofwork is being worked on/was worked on, given work unit of work wasviewed, a given unit of work was selected, how long the given unit ofwork has been idle, a last interaction parameter indicating when andwhat user last interacted with the given unit of work, users thatinteracted with the given unit of work, and/or other interactionparameters indicating sources of the interactions, context of theinteractions, content of the interactions and/or time for theinteractions), one or more file attachments, notification settings,privacy, an associated URL, one or more interaction parameters (e.g.,sources of the interactions, context of the interactions, content of theinteractions, time for the interactions, and/or other interactionparameters), updates, ordering of units of work within a given unit ofwork (e.g., tasks within a project, subtasks within a task, etc.,),state of a workspace for a given unit of work (e.g., application stateparameters, application status, application interactions, and/or otherparameters related to the state of the workspace for a unit of work),dependencies between one or more work units, one or more custom fields(e.g., priority, cost, stage, and/or other custom fields), quantities ofwork production for the unit of work (e.g., quantity of lines of code,quantity of lines of copy, etc.), other work unit parameters for thegiven work units, and/or other work unit parameters, and/or userparameters for one or more users and/or work units the given project isassociated with.

The values of the work assignment parameter describing units of workassigned to the individual users may be determined based on one or moreinteractions by one or more users with a collaboration environment. Insome implementations, one or more users may create and/or assign one ormore unit of work to themselves and/or an other user. In someimplementations, a user may be assigned a unit of work and the user mayeffectuate a reassignment of the unit of work from the user or one ormore other users.

In some implementations, values of the work assignment parameter mayindicate that a status parameter of a unit of work has changed from“incomplete” to “marked complete” and/or “complete”. In someimplementations, a status of complete for a unit of work may beassociated with the passing of an end date associated with the unit ofwork. In some implementations, a status of “marked complete” may beassociated with a user providing input via the collaboration environmentat the point in time the user completes the unit of work (which may bebefore or after an end date).

The meeting component 110 may be configured to determine and/or obtainuser input information and/or other information. The user inputinformation may convey user input from individual users to initiateindividual group meetings. By way of non-limiting illustration, the userinput information may convey the user input from a first user toinitiate a first group meeting with a first group of users. In someimplementations, initiating individual group meetings may be based onone or more of an identification of the users in a group, anidentification of one or more work unit records and/or units of worklinked to one or more users, and/or other processes. That is, one ormore users belonging to a group may not need to be known at the time ofinitiating the individual group meeting, but may be determined afterand/or concurrently with the user input initiating the individual groupmeeting.

In some implementations, the meeting component 110 may be configured toobtain user role information and/or other information. The user roleinformation may be obtained from environment state component 108. Theuser role information may specify individual roles of the individualusers. In some implementations, accessibility to provide the user inputto initiate individual group meetings may be limited to the users of agiven role. Initiation of the individual group meetings may be based onthe user role information of the individual users. For example, a userhaving an “intern” role and/or other role may not be providedaccessibility to initiate a meeting. A user having a “manager” roleand/or other role may be provided accessibility to initiate a meeting.

In some implementations, the accessibility to provide the user input toinitiate individual group meetings may be limited to the users of agiven role and/or may be limited to meetings with users of one or moreother given roles. For example, the user having the “intern” role maynot be provided accessibility to initiate a meeting with a user having a“CEO” role but may be provided accessibility to initiate a meeting withthe user having the “manager” role. Such accessibilities to provide theuser input to initiate individual group meetings may be modified (e.g.,a particular user having an “intern” role may initiate meetings with anyuser or with particular other users), enabled for a limited period oftime, enabled indefinitely, and/or fixed by an administrator of thesystem 100.

In some implementations, user input from individual users to initiateindividual group meetings may be facilitated in a variety of ways. Insome implementations, user input may be facilitated by user entry and/orselection of a user interface element (e.g., a virtual button, and/orother user interface elements described herein). In someimplementations, a user interface element to initiate individual groupmeetings may be presented in one or more of individual user record pagesfor individual user records, individual work unit record pages forindividual work unit records, individual work unit pages for individualunits of work, and/or other pages and/or user interface portions of acollaboration environment.

In some implementations, an individual user record page for anindividual user record may comprise a dashboard and/or other view wherethe individual user record (e.g., values of one or more user parametersand/or other information) for an individual user may be viewed,accessed, modified, and/or otherwise interacted with in other ways. Insome implementations, a user interface element to initiate individualgroup meetings presented within an individual user record page of anindividual user record of a user may be specific to the user of theindividual user record. By way of non-limiting illustration, the userinterface element may facilitate initiating an individual group meetingwhich includes that user specifically. The user interface element mayinclude indicia on the user interface element conveying the specificityto that user which may include, for example, “Schedule a group meetingwith User X” (where “User X” is the name and/or username of the specificuser). Accordingly, an other user may navigate to the user record pageof the user and initiate a group meeting with the user and or otherusers by selecting the user interface element.

In some implementations, an individual work unit record page for anindividual work unit record may comprise a dashboard and/or other viewwhere the individual work unit record (e.g., values of one or more workunit parameters and/or other information) may be viewed, accessed,modified, and/or interacted with in other ways. In some implementations,a user interface element to initiate individual group meetings presentedwithin an individual work unit record page of an individual work unitrecord may be specific to that individual work unit record. By way ofnon-limiting illustration, the user interface element may facilitateinitiating an individual group meeting with a group of users linked tothat work unit record. The user interface element may include indicia onthe user interface element conveying the specificity to that work unitrecord which may include, for example, “Schedule meeting with userslinked to this work unit record”. Accordingly, an other user maynavigate to the work unit record page and initiate a group meeting withthe group of users linked to the work unit record by selecting the userinterface element. In this manner, the other user initiating the meetingmay not yet be aware of the users with whom they are initiating thegroup meeting. For example, the other user may desire to merely have agroup meeting about a particular work unit record and/or group of workunit records, where the other parties may be unknown initially. By wayof non-limiting illustration, after selecting the user interfaceelement, the other user may be prompted with a pop up window (and/orother user interface element) where the group of users linked with awork unit record and/or group of work unit records may be shown. Theother user may then select one or more users from the pop up window withwhom they want to have the group meeting.

In some implementations, an individual work unit page for an individualunit of work may comprise a dashboard and/or other view where theindividual unit of work (e.g., values of one or more work unitparameters and/or other information) may be viewed, accessed, modified,and/or interacted with in other ways. An individual work unit page maycomprise a user interface where an individual unit of work is worked onby one or more users. By way of non-limiting illustration, an individualwork unit page may show values of one or more work unit parametersincluding one or more of title, description, assignee, assignor, startdate, due date, and/or other values. A work unit page of a unit of workmay differ from a work unit record page for a work unit record for thatunit of work in that the individual work unit record page may be a morerobust view of the unit of work, e.g., showing more and/or differentinformation about the unit of work than may appear in the work unitpage. That is, the work unit page may show information necessary for anassignee to complete the unit of work (e.g., a subset of the values ofthe work unit parameters, including one or more of title, description,assignee, assignor, start date, due date, and/or other values), whilethe work unit record page may show a more complete view of the unit ofwork such as a complete set of values of one or more parameters,metadata, and/or other information.

In some implementations, a user interface element to initiate individualgroup meetings presented within an individual work unit page of anindividual unit of work may be specific to that individual unit of workand/or a particular users linked to that individual unit of work (e.g.,assignee, assignor, and/or other users). By way of non-limitingillustration, the user interface element may facilitate initiating anindividual group meeting with an assignee of the unit of work and/orother users linked to the unit of work. The user interface element mayinclude indicia on the user interface element conveying the specificityto that unit of work which may include, for example, “Schedule meetingwith assignee of Task A and other users” (where “Task A” is the unit ofwork associated with the work unit page). Accordingly, an other user maynavigate to the work unit page and initiate a group meeting including atleast the assignee of the unit of work (and/or other users linked to theunit of work) by selecting the user interface element.

The work unit component 112 may identify the individual groups of userscorresponding to the individual group meetings. The work unit component112 may identify the individual groups of users corresponding to theindividual group meetings in response to obtaining the user inputinformation (e.g., in response to receiving the user input to initiatethe individual group meetings). In some implementations, identifying theindividual groups of users corresponding to the individual groupmeetings may be based on identifying users linked to a particular unitof work and/or work unit record.

In some implementations, identifying the individual groups of userscorresponding to the individual group meetings may be based on userinput from the individual users including entry and/or selection toidentify one or more of the users for inclusion in the individual groupmeetings. In some implementations, the user input may include entryand/or selection to identify the users for inclusion in an individualgroup (including a group designation and/or other information). In someimplementations, the entry and/or selection to identify the users forinclusion in a group may be done prior to and/or concurrently with theuser input to initiate the individual group meetings. By way ofnon-limiting illustration, leading up to a desire to initiate anindividual group meeting, a user may provide entry and/or selection toidentify a group of users for inclusion in a forthcoming individualgroup meeting.

In some implementations, responsive to obtaining the user input from theindividual users including the entry and/or selection to identify theusers for inclusion in the individual group meetings, meeting component110 may be configured to specify individual values of a meetingparameter for the individual users to reflect the inclusion in theindividual group meetings. The value of the meeting parameter may be,for example, quantitative (e.g., “0” meaning not included in theindividual group meeting, “1” meaning included in the individual groupmeeting), qualitative (e.g., “mtg” meaning to be included in theindividual group meeting, “nomtg” meaning to not be included in theindividual group meeting), a value specifying a group they are includedwith (by a name of the group and/or team, serial number, and/or othervalue identifying a specific group), and/or other values that mayreflect inclusion, or lack thereof, in the individual group meetings. Insome implementations, the entry and/or selection to identify the userfor inclusion in the individual group meetings may be based on entryand/or selection of a user interface element presented on one or more ofa work unit record page, a work unit page, user record page, and/orother views within a collaboration environment. By way of non-limitingillustration, a user interface element may include a check box (and/orother user interface element) which the selection thereof may cause theidentification for inclusion in the individual group meetings.Accordingly, meeting component 110 may be configured to identifyindividual users for inclusion in individual group meetings based onindividual user records specifying the individual values of the meetingparameter reflecting inclusion in the individual group meetings.

The work unit component 112 may identify the work unit recordscorresponding to the users of the individual group meetings. The workunit component 112 may identify the work unit records corresponding tothe users of the individual group meetings in response to obtaining theuser input information (e.g., in response to receiving the user input toinitiate the individual group meetings). The work unit records beingidentified may be ones linked to one of the users of the individualgroup meetings. The work unit records being identified may correspond tosubordinate ones of the users (e.g., based on role).

In some implementations, the work unit records being identified maycorrespond to a set of work unit records within a record hierarchy. Byway of non-limiting illustration, responsive to identifying a work unitrecord, one or more other work unit records which are part of a commonrecord hierarchy may be identified.

In some implementations, identifying the work unit records correspondingto one or more users of the individual group meetings (i.e., by workunit component 112) may include determining a date range and/or one ormore particular dates. The work unit records being identified maycorrespond to a set of work unit records tailored to the date rangeand/or one or more particular dates. This may allow a user to tailor agroup meeting to recent, current, and/or further work unit records asopposed to all work units records (e.g., which may include records toofar into the past and/or future). The date range and/or the one or moreparticular dates may specify a range of particular start dates for unitsof work, a range of particular end dates for units of work, and/or both.In some implementations, the date range may be specified by theindividual users providing the user input to initiate the individualgroup meetings. In some implementations, the one or more particulardates may be specified by the individual users providing the user inputto initiate the individual group meetings and/or the users of theindividual group meetings. Thus, work unit component 112 may beconfigured to identify the work unit records for the units of workhaving start dates and/or end dates that fall within the date range,and/or identify the work unit records for units of work having aparticular start date and/or a particular end date.

In some implementations, a date range in which work unit records may beidentified for an individual group meeting may be a range between a dateof a prior group meeting and a current date. This may facilitate thestreamlining of recurring group meetings where progress following priormeetings may be reviewed and/or evaluated by looking at the work unitrecords occurring after the prior meetings.

In some implementations, the work unit component 112 may identify thework unit records corresponding to the users of the individual groupmeetings based on user input from the individual users and/or otherinformation. In some implementations, the user input may include entryand/or selection to identify the work unit records for inclusion in theindividual group meetings. In some implementations, the entry and/orselection to identify the work unit records for inclusion in theindividual group meetings may be done prior to and/or concurrently withthe user input to initiate the individual group meetings. By way ofnon-limiting illustration, leading up to a desire to initiate anindividual group meeting, a user may provide entry and/or selection toidentify one or more work unit records for inclusion in a forthcomingindividual group meeting. In this way, a user may tailor a meeting tospecific work unit records based on their specific selection of workunit records.

In some implementations, responsive to obtaining the user input from theindividual users including the entry and/or selection to identify thework unit records for inclusion in the individual group meetings, workunit component 112 may be configured to specify individual values of ameeting parameter for the individual units of work to reflect theinclusion in the individual group meetings. The value of the meetingparameter may be, for example, quantitative (e.g., “0” meaning notincluded in the individual group meeting, “1” meaning included in theindividual group meeting), qualitative (e.g., “mtg” meaning to beincluded in the individual group meeting, “nomtg” meaning to not beincluded in the individual group meeting), and/or other values that mayreflect inclusion, or lack thereof, in the individual group meetings. Insome implementations, the entry and/or selection to identify the workunit records for inclusion in the individual group meetings may be basedon entry and/or selection of a user interface element presented on oneor more of a work unit record page, a work unit page, and/or other viewswithin a collaboration environment. By way of non-limiting illustration,a user interface element may include a check box (and/or other userinterface element) which the selection thereof may cause theidentification for inclusion in the individual group meetings.Accordingly, work unit component 112 may be configured to identifyindividual work unit records for inclusion in individual group meetingsbased on individual work unit records specifying the individual valuesof the meeting parameter reflecting inclusion in the individual groupmeetings.

In some implementations, work unit component 112 may be configured toidentify the work unit records corresponding to the individual groupmeetings, then identify the individual groups of users corresponding tothe individual group meetings by identifying the users linked to thework unit records identified as corresponding to the individual groupmeetings.

In some implementations, work unit component 112 may be configured toidentify the individual groups of users corresponding to the individualgroup meetings, then identify the work unit records corresponding to theindividual group meetings by identifying the work unit records linked tothe users in the individual groups of users identified as correspondingto the individual group meetings.

By way of non-limiting illustration, responsive to obtaining the userinput from the first user, work unit component 112 may be configured toidentify the users in the first group of users and/or a first set ofwork unit records for the first group meeting.

The agenda generation component 114 may be configured to generate agendainformation and/or other information for the individual group meetings.The agenda information may define individual agendas for the individualgroup meetings. The individual agendas may include sets of agenda itemsand/or other items for the individual group meetings. Individual agendaitems may correspond to an individual work unit record and/or userrecord having been identified as corresponding to one or more users ofthe individual group meetings. The individual agenda items may includeand/or facilitate access to the corresponding ones the records. Forexample, an individual agenda item may include a corresponding work unitrecord on the agenda and/or the individual agenda item may include alink (e.g., hyperlink, pointer, resource identifier, etc.) to access thecorresponding work unit record. In some implementations, thecorresponding work unit record included on the agenda may include one ormore of a summary of the work unit record, a copy of the work unitrecord, and/or other information. A summary of the work unit record mayinclude values of a subset of parameters deemed of most importance.Importance may be specified by a user and/or an administrator of thesystem. A copy of the work unit record may be utilized to ensure theactual work unit record is not accidentally modified, deleted, and/orotherwise interacted with in unintended ways. Work unit records and/orother records may be represented in agendas in other ways.

By way of non-limiting illustration, the agenda information may define afirst agenda for the first group meeting. The first agenda may include afirst set of agenda items and/or other information. Individual agendaitems in the first set of agenda items may correspond to individual workunit records in the first set of work unit records and/or otherinformation.

In some implementations, agenda generation component 114 may beconfigured to obtain performance information for the individual users.The agenda generation component 114 may be configured such that theagenda information for the individual group meetings include theperformance information for at least one of the users of the individualgroup meetings. The performance information may include one or moreperformance metrics for the individual users. A performance metric maybe expressed in a variety of ways. By way of non-limiting illustration,a performance metric may include a measure based on one or more of howmany days of work the user has missed, how many units of work have beencompleted in a given period of time, how many units of work have beencompleted on or prior to a due date within a given period of time,reviews submitted by other users (e.g., from a performance reviewquestionnaire), and/or other measures. The above description ofperformance metrics is not intended to be limiting. Instead, it is to beunderstood that other types of performance metrics may be utilized forthe purpose of inclusion in an agenda of a group meeting as needed forreview and/or evaluation of a user.

In some implementations, agenda generation component 114 may beconfigured to obtain scheduling information and/or other information forthe individual users. The scheduling information may be obtained fromthe environment state component 108 and/or from external resources 126.The scheduling information may include one or more of one or morecalendar entries, individual calendar entries being specified withinand/or outside the collaboration environment, and/or other schedulinginformation for the individual users. The agenda generation component114 may be configured to determine individual group meeting times forthe individual group meetings based on the scheduling information of agroup of users. The individual group meeting times may be determinedbased on co-availability of the users of the individual group meetings.In some implementations, the meeting times may be automaticallydetermined. In some implementations, the meeting times may be proposedand communicated to one or more users. The users may have an opportunityto confirm and/or request changes to the meeting times. In someimplementations, based on meeting times for the individual groupmeeting, the scheduling information may be updated and/or edited toinclude one or more calendar entries for the users in the individualgroup meetings at the scheduled times.

In some implementations, the agenda generation component 114 may beconfigured to generate meeting-specific units of work for the individualgroup meetings. The meeting-specific units of work may include one ormore of the agenda information, requests to obtain particularinformation prior to the individual group meeting, requests to reviewparticular information prior to the individual group meeting, requeststo note details from the individual group meetings subsequent to theindividual group meetings, and/or other information. Themeeting-specific units of work may be dated for the individual groupmeeting times, a particular time prior to the individual group meetingtimes, a particular time subsequent to the individual group meetingtime, and/or other times. The meeting-specific units of work may bepresented to the individual users of the individual group meetings via auser interface for the collaboration environment.

Environment state component 108 may be configured to effectuatepresentation of individual user interfaces on individual clientcomputing platforms of one or more client computing platforms 104. Theindividual client computing platforms may access a user interface overnetwork 116. A user interface may include one or more user interfaceportions. By way of non-limiting illustration, a user interface mayinclude one or more of an input portion, a display portion, and/or otherportions. Individual portions may include one or more user interfaceelements configured to facilitate user interaction with the userinterface. By way of non-limiting illustration, user interface elementsmay include one or more of text input fields, drop down menus, checkboxes, display windows, pop up windows, virtual buttons, and/or otherelements configured to facilitate user interaction.

An input portion of a user interface may be configured to obtain userinput comprising user entry and/or selection of information (e.g.,identifications of users, date/time entries, and/or other information).The input portion may comprise one or more text input fields, one ormore check boxes, one or more drop down menus, and/or other userinterface elements configured to accept user entry and/or selection ofinformation.

A display portion may be configured to display a visualization of thescheduling information, one or more units of work, performanceinformation, work unit record pages, user record pages, work unit pages,agenda, agenda information, and/or other features described herein.

FIG. 3 illustrates a user interface 300, in accordance with one or moreimplementations. The user interface 300 may display a work unit page fora first unit of work. The user interface 300 may display differentvalues of one or more work unit parameters of the first unit of work,and/or other information. By way of non-limiting illustration, a userinterface element 302 may display a title of the first unit of work(e.g., Task Y). A user interface element 304 may display an assignee ofthe first unit of work (e.g., User A). A user interface element 306 maydisplay an assignor of the first unit of work (e.g., User B). A userinterface element 308 may display a due date of the first unit of work.A user interface element 310 may display a description of the first unitof work. A user interface element 314 may be configured to obtain userinput to identify a work unit record for the first unit of work forinclusion in a meeting. Responsive to obtaining the user input, a valueof a meeting parameter for the first unit of work may be specified toreflect the inclusion in a meeting.

A user interface element 312 may be configured to obtain user input toinitiate a group meeting with users linked to the first unit of work.The user linked to the first unit of work may include one or more of theassignee, assignor, and/or other users linked to the first unit of work.The users linked to the first unit of work may default to one or more ofthe assignee, assignor, a manager, a creator, and/or other users linkedto the first unit of work. Responsive to the user input, a group ofusers may be identified. The group of users may include one or more ofthe assignee, assignor, and/or other information. As such, a user maynavigate to the work unit page and select the user interface element 312to schedule a meeting with users linked to the first unit of work.

It is noted that FIG. 3 is for illustrative purposes only and is not tobe considered limiting. Instead, it is to be understood that the userinterface 300 may be configured in other ways and/or including otherelements in accordance with one or more implementations of the system100 presented herein.

FIG. 4 illustrates an exemplary user interface 400 generating agendasfor group meetings, in accordance with one or more implementations. Theuser interface 400 may facilitate obtaining user input to initiate ameeting and/or modify agenda information and/or other information abouta group meeting (e.g., Meeting B). The user interface 400 may includeone or more of a meeting window 402, a task list window 412 displaying aset of units of work for a first user (e.g., User A), a task list window413 displaying a set of units of work for a second user (e.g., User B),a meeting agenda window 414, and/or other user interface elements.Meeting window 402 may facilitate initiating and/or making changes toindividual group meetings by individual users. Meeting window 402 mayrepresent a window that may pop up responsive to selection of userinterface element 312 in FIG. 3. Meeting window 402 may include userinterface elements 404, 405, 406, 408, and/or 410. User interfaceelement 404 (e.g., a dropdown menu) may facilitate user entry and/orselection of a user (e.g., User A) included in the group meeting. Userinterface element 405 (e.g., a dropdown menu) may facilitate user entryand/or selection of an other user (e.g., User B) included in the groupmeeting. User interface element 406 may facilitate user entry of a datefor the meeting (e.g., Date C). User interface element 408 mayfacilitate user entry of one or more of a date range and/or a date ofwhich work unit records (described for illustrative purposes as“task(s)”) may be identified to be included in agenda information forthe meeting. The meeting may be changed, initiated, and/or scheduledupon selection of user interface element 410 and the agenda information(e.g., in meeting agenda window 414) may be generated. The agendainformation may include agenda items (e.g., items 1 and/or 2). Based onthe user entry via user interface element 408 (e.g., February 7-14), theagenda items may facilitate access to units of work created by, assignedto, and/or completed by User A and User B within the date range(s)identified (e.g., Task X and/or Task Y) for inclusion in the meeting asshown in meeting agenda window 414.

It is noted that FIG. 4 is for illustrative purposes only and is not tobe considered limiting. Instead, it is to be understood that the userinterface 400 may be configured in other ways and/or including otherelements in accordance with one or more implementations of the system100 presented herein.

FIG. 5 illustrates a user interface 500 generating agendas for groupmeetings, in accordance with one or more implementations. The userinterface 500 may display a meeting window 502, a scheduling window 512,and a meeting agenda window 514. Meeting window 502 may facilitateinitiating and/or making changes to individual group meetings (e.g.,Meeting E) by a group of users. Meeting window 502 may include userinterface elements 504, 506, 508, and 510. User interface element 504(e.g., a dropdown menu) may facilitate user entry and/or selection of auser (e.g., User A from FIG. 4) to include in the group meeting. Userinterface element 505 (e.g., a dropdown menu) may facilitate user entryand/or selection of an other user (e.g., User B from FIG. 4) to includein the group meeting. User interface element 506 may facilitate userentry and/or selection of a date for the meeting. Upon selection of userinterface element 506, scheduling information may be presented inscheduling window 512. Scheduling information may provide availability,for example, of User A, User B, and the initiator of the group meetingto facilitate determining a meeting date and/or time. User interfaceelement 508 may facilitate user entry of one or more of a date rangeand/or a date of which work unit records may be identified to beincluded in agenda information for the meeting (e.g., tasks sinceMeeting B of FIG. 4). The meeting may be initiated, changed, and/orscheduled upon selection of user interface element 510 and the agendainformation (e.g., shown in meeting agenda window 514) may be generated.The agenda information in meeting agenda window 514 may include agendaitems (e.g., items 1 and 2). Based on the user entry via user interfaceelement 508 (e.g., Since Meeting B), the agenda items may facilitateaccess to units of work created by, assigned to, and/or completed byUser A and/or User B since Meeting B of FIG. 4. The agenda informationmay further include an agenda item that facilitates access toperformance information of User A and/or User B (e.g., item 2).

It is noted that FIG. 5 is for illustrative purposes only and is not tobe considered limiting. Instead, it is to be understood that the userinterface 500 may be configured in other ways and/or including otherelements in accordance with one or more implementations of the system100 presented herein.

Returning to FIG. 1, in some implementations, server(s) 102, clientcomputing platform(s) 104, and/or external resources 126 may beoperatively linked via one or more electronic communication links. Forexample, such electronic communication links may be established, atleast in part, via a network 116 such as the Internet and/or othernetworks. It will be appreciated that this is not intended to belimiting, and that the scope of this disclosure includes implementationsin which server(s) 102, client computing platform(s) 104, and/orexternal resources 126 may be operatively linked via some othercommunication media.

A given client computing platform may include one or more processorsconfigured to execute computer program components. The computer programcomponents may be configured to enable an expert or user associated withthe given client computing platform to interface with system 100 and/orexternal resources 126, and/or provide other functionality attributedherein to client computing platform(s) 104. By way of non-limitingexample, the given client computing platform 104 may include one or moreof a desktop computer, a laptop computer, a handheld computer, a tabletcomputing platform, a NetBook, a Smartphone, a gaming console, and/orother computing platforms.

External resources 126 may include sources of information outside ofsystem 100, external entities participating with system 100, and/orother resources. In some implementations, some or all of thefunctionality attributed herein to external resources 126 may beprovided by resources included in system 100.

Server(s) 102 may include electronic storage 128, one or more processors130, and/or other components. Server(s) 102 may include communicationlines, or ports to enable the exchange of information with a network 116and/or other computing platforms. Illustration of server(s) 102 in FIG.1 is not intended to be limiting. Server(s) 102 may include a pluralityof hardware, software, and/or firmware components operating together toprovide the functionality attributed herein to server(s) 102. Forexample, server(s) 102 may be implemented by a cloud of computingplatforms operating together as server(s) 102.

Electronic storage 128 may comprise non-transitory storage media thatelectronically stores information. The electronic storage media ofelectronic storage 128 may include one or both of system storage that isprovided integrally (i.e., substantially non-removable) with server(s)102 and/or removable storage that is removably connectable to server(s)102 via, for example, a port (e.g., a USB port, a firewire port, etc.)or a drive (e.g., a disk drive, etc.). Electronic storage 128 mayinclude one or more of optically readable storage media (e.g., opticaldisks, etc.), magnetically readable storage media (e.g., magnetic tape,magnetic hard drive, floppy drive, etc.), electrical charge-basedstorage media (e.g., EEPROM, RAM, etc.), solid-state storage media(e.g., flash drive, etc.), and/or other electronically readable storagemedia. Electronic storage 128 may include one or more virtual storageresources (e.g., cloud storage, a virtual private network, and/or othervirtual storage resources). Electronic storage 128 may store softwarealgorithms, information determined by processor(s) 130, informationreceived from server(s) 102, information received from client computingplatform(s) 104, and/or other information that enables server(s) 102 tofunction as described herein.

Processor(s) 130 may be configured to provide information processingcapabilities in server(s) 102. As such, processor(s) 130 may include oneor more of a digital processor, an analog processor, a digital circuitdesigned to process information, an analog circuit designed to processinformation, a state machine, and/or other mechanisms for electronicallyprocessing information. Although processor(s) 130 is shown in FIG. 1 asa single entity, this is for illustrative purposes only. In someimplementations, processor(s) 130 may include a plurality of processingunits. These processing units may be physically located within the samedevice, or processor(s) 130 may represent processing functionality of aplurality of devices operating in coordination. Processor(s) 130 may beconfigured to execute components 108, 110, 112, 114, and/or othercomponents. Processor(s) 130 may be configured to execute components108, 110, 112, and/or 114, and/or other components by software;hardware; firmware; some combination of software, hardware, and/orfirmware; and/or other mechanisms for configuring processingcapabilities on processor(s) 130. As used herein, the term “component”may refer to any component or set of components that perform thefunctionality attributed to the component. This may include one or morephysical processors during execution of processor readable instructions,the processor readable instructions, circuitry, hardware, storage media,or any other components.

It should be appreciated that although components 108, 110, 112, and/or114 are illustrated in FIG. 1 as being implemented within a singleprocessing unit, in implementations in which processor(s) 130 includesmultiple processing units, one or more of components 108, 110, 112,and/or 114 may be implemented remotely from the other components. Thedescription of the functionality provided by the different components108, 110, 112, and/or 114 described below is for illustrative purposes,and is not intended to be limiting, as any of components 108, 110, 112,and/or 114 may provide more or less functionality than is described. Forexample, one or more of components 108, 110, 112, and/or 114 may beeliminated, and some or all of its functionality may be provided byother ones of components 108, 110, 112, and/or 114. As another example,processor(s) 130 may be configured to execute one or more additionalcomponents that may perform some or all of the functionality attributedbelow to one of components 108, 110, 112, and/or 114.

FIG. 2 illustrates a method 200 to generate agendas for group meetings,in accordance with one or more implementations. The operations of method200 presented below are intended to be illustrative. In someimplementations, method 200 may be accomplished with one or moreadditional operations not described, and/or without one or more of theoperations discussed. Additionally, the order in which the operations ofmethod 200 are illustrated in FIG. 2 and described below is not intendedto be limiting.

In some implementations, method 200 may be implemented in one or moreprocessing devices (e.g., a digital processor, an analog processor, adigital circuit designed to process information, an analog circuitdesigned to process information, a state machine, and/or othermechanisms for electronically processing information). The one or moreprocessing devices may include one or more devices executing some or allof the operations of method 200 in response to instructions storedelectronically on an electronic storage medium. The one or moreprocessing devices may include one or more devices configured throughhardware, firmware, and/or software to be specifically designed forexecution of one or more of the operations of method 200.

An operation 202 may manage environment state information maintaining acollaboration environment. The collaboration environment may beconfigured to facilitate interaction by users with the collaborationenvironment. Operation 202 may be performed by one or more hardwareprocessors configured by machine-readable instructions including acomponent that is the same as or similar to environment state component108, in accordance with one or more implementations.

An operation 204 may obtain user input information conveying user inputfrom individual users to initiate individual group meetings. Operation204 may be performed by one or more hardware processors configured bymachine-readable instructions including a component that is the same asor similar to meeting component 110, in accordance with one or moreimplementations.

An operation 206 may identify the individual groups of userscorresponding to the individual group meetings and/or identify the workunit records corresponding to the individual group meetings. Operation206 may be performed by one or more hardware processors configured bymachine-readable instructions including a component that is the same asor similar to work unit component 112, in accordance with one or moreimplementations.

An operation 208 may generate agenda information defining individualagendas for the individual group meetings. The individual agendas mayinclude individual sets of agenda items. Operation 208 may be performedby one or more hardware processors configured by machine-readableinstructions including a component that is the same as or similar toagenda generation component 114, in accordance with one or moreimplementations.

Although the present technology has been described in detail for thepurpose of illustration based on what is currently considered to be themost practical and preferred implementations, it is to be understoodthat such detail is solely for that purpose and that the technology isnot limited to the disclosed implementations, but, on the contrary, isintended to cover modifications and equivalent arrangements that arewithin the spirit and scope of the appended claims. For example, it isto be understood that the present technology contemplates that, to theextent possible, one or more features of any implementation can becombined with one or more features of any other implementation.

What is claimed is:
 1. A system configured to generate agendas for groupmeetings, the system comprising: one or more physical processorsconfigured by machine-readable instructions to: manage, at a server,environment state information maintaining a virtual collaborationenvironment, the virtual collaboration environment being configured tofacilitate interaction by users with the virtual collaborationenvironment by accessing the virtual collaboration environment viaremotely located client computing platforms associated with the usersover an Internet connection, the environment state information includingwork unit records of units of work created by the users, and assignedwithin the virtual collaboration environment to the users who areexpected to accomplish one or more actions to complete the units ofwork, such that the work unit records include a first set of work unitrecords for a first set of units of work previously assigned to a firstset of users who are expected to accomplish a first set of actions tocomplete the first set of units of work; establish the Internetconnection between the server and the remotely located client computingplatforms; effectuate, at the remotely located client computingplatforms, presentation of a user interface of the virtual collaborationenvironment through which the users access the work unit records for theunits of work, the user interface including a user-selectable interfaceelement configured to initiate individual group meetings with individualgroups of users, such that the user interface presents a first work unitpage for a first work unit record included in the first set of work unitrecords; obtain, at the server, user input information conveying userinput into the user interface at the remotely located client computingplatforms to initiate the individual group meetings with the individualgroups of users, such that the user input information conveys the userinput from a first user into the first work unit page to initiate afirst group meeting with a first group of users, the user input from thefirst user including selection of the user-selectable interface elementpresented within the first work unit page; responsive to obtaining theuser input information: identify, at the server, the individual groupsof users corresponding to the individual group meetings; and/oridentify, at the server, the work unit records corresponding to theindividual group meetings; such that responsive to obtaining the userinput from the first user, identify the first set of users as the firstgroup of users for the first group meeting and/or identify the first setof work unit records as corresponding the first group meeting; generate,at the server, individual agendas for the individual group meetingsbased on the units of work previously assigned to the users within thevirtual collaboration environment, the individual agendas beinggenerated by determining individual sets of agenda items for theindividual agendas, an individual agenda item corresponding to anindividual work unit record corresponding to an individual groupmeeting, wherein individual agenda items facilitate access to thecorresponding ones of the work unit records for the units of workpreviously assigned to the users, such that a first agenda for the firstgroup meeting is generated, the first agenda being generated bydetermining a first set of agenda items, the first set of agenda itemscorresponding to the work unit records in the first set of work unitrecords for the first set of units of work previously assigned to thefirst set of users, the first set of agenda items including a firstagenda item corresponding to a second work unit record included in thefirst set of work unit records, wherein the first agenda itemfacilitates access to the second work unit record; and effectuate, atthe remotely located client computing platforms, presentation of ameeting agenda window presenting the individual agendas, the individualagendas being displayed in the meeting agenda window by including theindividual sets of agenda items for the individual agendas, whereinselection of the individual agenda items in the meeting agenda windowfacilitates access to the corresponding ones of the work unit records bypresenting individual work unit pages of the corresponding ones of thework unit records, such that selection of the first agenda item causespresentation of a second work unit page through with the users in thefirst set of users access the second work unit record.
 2. The system ofclaim 1, wherein the one or more physical processors are furtherconfigured by the machine-readable instructions to: obtain schedulinginformation for individual users in the individual groups of users, thescheduling information including one or more calendar entries,individual calendar entries being specified within and/or outside thevirtual collaboration environment; and determine individual meetingtimes for the individual group meetings based on the schedulinginformation for the individual groups of users associated with theindividual group meetings.
 3. The system of claim 1, wherein identifyingthe work unit records corresponding to the individual group meetingsand/or identifying the individual groups of users corresponding to theindividual group meetings comprises: identifying the work unit recordscorresponding to the individual group meetings; then identifying theindividual groups of users corresponding to the individual groupmeetings by identifying the users assigned to the work units recordsidentified as corresponding to the individual group meetings.
 4. Thesystem of claim 3, wherein identifying the work unit recordscorresponding to the individual group meetings includes: determining adate range; and identifying the work unit records for the units of workhaving start dates and/or end dates that fall within the date range,such that the first set of units of work falls within the date range. 5.The system of claim 3, wherein identifying the work unit recordscorresponding to the individual group meetings is based on the userinput from individual users further including entry and/or selection toidentify the work unit records for inclusion in the individual groupmeetings; and the one or more physical processors are further configuredby the machine-readable instructions to: responsive to obtaining theuser input from the individual users including the entry and/orselection to identify the work unit records for inclusion in theindividual group meetings: specify, within the individual work unitrecords, individual values of a meeting parameter for the individualunits of work to reflect the inclusion in the individual group meetings.6. The system of claim 1, wherein identifying the work unit recordscorresponding to the individual group meetings and/or identifying theindividual groups of users corresponding to the individual groupmeetings comprises: identifying the individual groups of userscorresponding to the individual group meetings; then identifying thework unit records corresponding to the individual group meetings byidentifying the work unit records assigned to the users in theindividual groups of users identified as corresponding to the individualgroup meetings.
 7. The system of claim 6, wherein identifying theindividual groups of users corresponding to the individual groupmeetings is based on the user input from individual users furtherincluding entry and/or selection to identify one or more of the usersfor inclusion in the individual group meetings; and the one or morephysical processors are further configured by the machine-readableinstructions to: responsive to obtaining the user input from theindividual users including the entry and/or selection to identify theone or more of the users for inclusion in the individual group meetings:specify, within individual user records, individual values of a meetingparameter for the one or more of the users to reflect the inclusion inthe individual group meetings.
 8. The system of claim 6, whereinidentifying the individual groups of users corresponding to theindividual group meetings is based on the individual groups of usersbeing part of a same team and/or working on a same project.
 9. Thesystem of claim 1, wherein the one or more physical processors arefurther configured by the machine-readable instructions to: generatemeeting-specific units of work of the individual group meetings, whereinthe meeting-specific units of work include agenda information and areassigned to the users in the individual groups of users of theindividual group meetings.
 10. The system of claim 1, wherein the one ormore physical processors are further configured by the machine-readableinstructions to: obtain user role information specifying individual roleof individual users; and wherein accessibility to provide the user inputto initiate the individual group meetings is limited to the users of agiven role.
 11. A method to generate agendas for group meetings, themethod comprising: managing, at a server, environment state informationmaintaining a virtual collaboration environment, the virtualcollaboration environment being configured to facilitate interaction byusers with the virtual collaboration environment by accessing thevirtual collaboration environment via remotely located client computingplatforms associated with the users over an Internet connection, theenvironment state information including work unit records of units ofwork created by the users, and assigned within the virtual collaborationenvironment to the users who are expected to accomplish one or moreactions to complete the units of work, such that the work unit recordsinclude a first set of work unit records for a first set of units ofwork previously assigned to a first set of users who are expected toaccomplish a first set of actions to complete the first set of units ofwork; establishing the Internet connection between the server and theremotely located client computing platforms; effectuating, at theremotely located client computing platforms, presentation of a userinterface of the virtual collaboration environment through which theusers access the work unit records for the units of work, the userinterface including a user-selectable interface element configured toinitiate individual group meetings with individual groups of users, suchthat the user interface presents a first work unit page for a first workunit record included in the first set of work unit records; obtaining,at the server, user input information conveying user input into the userinterface at the remotely located client computing platforms to initiatethe individual group meetings with the individual groups of users, theuser input information conveying the user input from a first user intothe first work unit page to initiate a first group meeting with a firstgroup of users, the user input from the first user including selectionof the user-selectable interface element presented within the first workunit page; responsive to obtaining the user input information:identifying, at the server, the individual groups of users correspondingto the individual group meetings; and/or identifying, at the server, thework unit records corresponding to the individual group meetings;including responsive to obtaining the user input from the first user,identifying the first set of users as the first group of users for thefirst group meeting and/or identifying the first set of work unitrecords as corresponding the first group meeting; generating individualagendas for the individual group meetings based on the units of workpreviously assigned to the users within the virtual collaborationenvironment, the individual agendas being generated by determiningindividual sets of agenda items for the individual agendas, anindividual agenda item corresponding to an individual work unit recordcorresponding to an individual group meeting, wherein individual agendaitems facilitate access to the corresponding ones of the work unitrecords for the units of work previously assigned to the users,including generating a first agenda for the first group meeting bydetermining a first set of agenda items, the first set of agenda itemscorresponding to the work unit records in the first set of work unitrecords for the first set of units of work previously assigned to thefirst set of users, the first set of agenda items including a firstagenda item corresponding to a second work unit record included in thefirst set of work unit records, wherein the first agenda itemfacilitates access to the second work unit record; and effectuating, atthe remotely located client computing platforms, presentation of ameeting agenda window presenting the individual agendas, the individualagendas being displayed in the meeting agenda window by including theindividual sets of agenda items for the individual agendas, whereinselection of the individual agenda items in the meeting agenda windowfacilitates access to the corresponding ones of the work unit records bypresenting individual work unit pages of the corresponding ones of thework unit records, such that selection of the first agenda item causespresentation of a second work unit page through with the users in thefirst set of users access the second work unit record.
 12. The method ofclaim 11, further comprising: obtaining scheduling information forindividual users in the individual groups of users, the schedulinginformation including one or more calendar entries, individual calendarentries being specified within and/or outside the virtual collaborationenvironment; and determining individual meeting times for the individualgroup meetings based on the scheduling information for the individualgroups of users associated with the individual group meetings.
 13. Themethod of claim 11, wherein identifying the work unit recordscorresponding to the individual group meetings and/or identifying theindividual groups of users corresponding to the individual groupmeetings comprises: identifying the work unit records corresponding tothe individual group meetings; then identifying the individual groups ofusers corresponding to the individual group meetings by identifying theusers assigned to the work units records identified as corresponding tothe individual group meetings.
 14. The method of claim 13, whereinidentifying the work unit records corresponding to the individual groupmeetings includes: determining a date range; and identifying the workunit records for the units of work having start dates and/or end datesthat fall within the date range, wherein the first set of units of workfalls within the date range.
 15. The method of claim 13, whereinidentifying the work unit records corresponding to the individual groupmeetings is based on the user input from individual users furtherincluding entry and/or selection to identify the work unit records forinclusion in the individual group meetings; and wherein the methodfurther comprises: responsive to obtaining the user input from theindividual users including the entry and/or selection to identify thework unit records for inclusion in the individual group meetings:specifying, within the individual work unit records, individual valuesof a meeting parameter for the individual units of work to reflect theinclusion in the individual group meetings.
 16. The method of claim 11,wherein identifying the work unit records corresponding to theindividual group meetings and/or identifying the individual groups ofusers corresponding to the individual group meetings comprises:identifying the individual groups of users corresponding to theindividual group meetings; then identifying the work unit recordscorresponding to the individual group meetings by identifying the workunit records assigned to the users in the individual groups of usersidentified as corresponding to the individual group meetings.
 17. Themethod of claim 16, wherein identifying the individual groups of userscorresponding to the individual group meetings is based on the userinput from individual users further including entry and/or selection toidentify one or more of the users for inclusion in the individual groupmeetings; and the method further comprises: responsive to obtaining theuser input from the individual users including the entry and/orselection to identify the one or more of the users for inclusion in theindividual group meetings: specifying, within individual user records,individual values of a meeting parameter for the one or more of theusers to reflect the inclusion in the individual group meetings.
 18. Themethod of claim 16, wherein identifying the individual groups of userscorresponding to the individual group meetings is based on theindividual groups of users being part of a same team and/or working on asame project.
 19. The method of claim 11, further comprising: generatingmeeting-specific units of work of the individual group meetings, whereinthe meeting-specific units of work include agenda information and areassigned to the users in the individual groups of users of theindividual group meetings.
 20. The method of claim 11, furthercomprising: obtaining user role information specifying individual roleof individual users; and wherein accessibility to provide the user inputto initiate the individual group meetings is limited to the users of agiven role.